Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-256649 | VCLD-70-000005 | SV-256649r888469_rule | Medium |
Description |
---|
Logging must be started as soon as possible when a service starts and when a service is stopped. Many forms of suspicious actions can be detected by analyzing logs for unexpected service starts and stops. Also, by starting to log immediately after a service starts, it becomes more difficult for suspicious activity to go unlogged. |
STIG | Date |
---|---|
VMware vSphere 7.0 VAMI Security Technical Implementation Guide | 2023-02-22 |
Check Text ( C-60324r888467_chk ) |
---|
At the command prompt, run the following command: # /opt/vmware/sbin/vami-lighttpd -p -f /opt/vmware/etc/lighttpd/lighttpd.conf 2>/dev/null|grep "server.errorlog"|sed -e 's/^[ ]*//' Expected result: server.errorlog = "/opt/vmware/var/log/lighttpd/error.log" If the output does not match the expected result, this is a finding. Note: The command must be run from a bash shell and not from a shell generated by the "appliance shell". Use the "chsh" command to change the shell for the account to "/bin/bash". Refer to KB Article 2100508 for more details: https://kb.vmware.com/s/article/2100508 |
Fix Text (F-60267r888468_fix) |
---|
Navigate to and open: /opt/vmware/etc/lighttpd/lighttpd.conf Add or reconfigure the following value: server.errorlog = "/opt/vmware/var/log/lighttpd/error.log" Restart the service with the following command: # vmon-cli --restart applmgmt |